So what's the actual reason to push this? Are there any new features you really need?

The big one for me is the feature-rich tables API. Very powerful for creating monitors and control panels for lots of elements/devices/agents etc. The previous columns API was rather clunky. There are also options to view-clip large lists. Other than that I've been inconvenienced more frequently by small quirks and issues that were addressed in later versions.

Thanks for the clarification, makes sense; I'm currently working on a lot of GUI specific code, probably good to merge this change into NAP and use that as a base instead of our current version of ImGUI, but that won't be immediately unfortunately because I'm rather busy getting some other things off the ground.

Trying your version, noticed that icons are rendered incorrect:

yours:

current:

Trying your version, noticed that icons are rendered incorrect:

This is because the API for ImGui::ImageButtonEx changed from

if (held || hovered)
	{
		const ImU32 col = GetColorU32(held ? ImGuiCol_ButtonActive : ImGuiCol_ButtonHovered);
		RenderFrame(bb.Min, bb.Max, col, true, ImClamp((float)ImMin(padding.x, padding.y), 0.0f, style.FrameRounding));
	}

to

const ImU32 col = GetColorU32((held && hovered) ? ImGuiCol_ButtonActive : hovered ? ImGuiCol_ButtonHovered : ImGuiCol_Button);
    RenderNavCursor(bb, id);
    RenderFrame(bb.Min, bb.Max, col, true, ImClamp((float)ImMin(padding.x, padding.y), 0.0f, g.Style.FrameRounding));

So it now defaults to defaults to ImGuiCol_Button when the button is untouched, which is an improvement imo. The custom palette we use assumes no transparency and writes 1.0 to the alpha channel of the front color in imguistyle.cpp.

ImVec4 IMGUI_NAPFRO1(palette.mFront1Color, 1.0f);

ioStyle.Colors[ImGuiCol_Button] = IMGUI_NAPFRO1;

Do you have thoughts on the best way forward?